chore(deps): align QPK pin to 31892425a022#124
Conversation
Automated downstream QPK pin update after QPK_PIN landed on main. Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Codex PR Review✅ Merge allowed: No issues found Review by Codex PR Review bot • PR |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8a046a4a47
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| requires-python = ">=3.11" | ||
| dependencies = [ | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@56a03364d517fd0e2efb2c4d4add8a785fc5e857", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@31892425a02242126265ac07a626d98796daa459", |
There was a problem hiding this comment.
In the checked .github/workflows/ci.yml step at lines 92-102, CI downloads QuantPlatformKit/main/QPK_PIN and passes it to check_qpk_pin_consistency.py; as of July 10, 2026 that upstream pin is still 56a03364d517fd0e2efb2c4d4add8a785fc5e857, so changing this repo to 31892425a022... makes every CI run report pyproject/uv.lock QPK mismatches. Unless the upstream QPK_PIN on main is updated first, or this workflow is changed to read the same QPK ref being reviewed, this pin bump cannot pass the required guard.
Useful? React with 👍 / 👎.
|
|
||
| [qsl.requires] | ||
| quant_platform_kit = "56a03364d517fd0e2efb2c4d4add8a785fc5e857" | ||
| quant_platform_kit = "31892425a02242126265ac07a626d98796daa459" |
There was a problem hiding this comment.
With enforce_bundle = true, bumping this repo to QPK 31892425... should also move the companion CryptoStrategies pin to the QSL pin set for that rollout, but this commit leaves every crypto-strategies reference at ef78312... (pyproject.toml, qsl.toml, and uv.lock). The CI workflow resolves and installs CryptoStrategies from that stale project pin while overriding it to the new QPK API, so contract tests and runtime execute an unvalidated mixed bundle instead of the paired strategy catalog.
Useful? React with 👍 / 👎.
1 participant
Summary
31892425a022uv.lock，同步刷新 lockfileTest plan
🤖 Generated with Claude Code